home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr25
/
atelnt.zip
/
ATELNET.DOC
< prev
next >
Wrap
Text File
|
1993-03-13
|
18KB
|
513 lines
ATELNET: AN APPC REMOTE TERMINAL FOR OS/2
June 10, 1992
Peter J. Schwaller
IBM Corporation
APPC Market Enablement
Department E42, Building 673
Research Triangle Park, North Carolina 27709
----------------------------------------------
Internet: pjs@ralvm6.vnet.ibm.com
CompuServe: 76711,371
IBM VNET: PJS at RALVM6
Phone: (919) 254-4376
IBM Tie-line: 8-444-4376
Abstract
This paper describes how to use and configure an an APPC application program
for OS/2 Extended Edition or Extended Services. The application, ATELNET,
provides remote terminal capability for OS/2, enabling you to log on to a
remote OS/2 workstation and execute programs on that workstation in a full-
screen session.
ATELNET is an extended APPC application, as opposed to many widely-available
APPC samples that do little more than transfer files. You can use ATELNET to
control multiple full-screen windows on another workstation. You can also
use it to start more than one full-screen application on either one work-
station or different workstations.
ATELNET was developed to provide more useful utilities for APPC. It also
helps demonstrate that applications for APPC can be more powerful and perform
better than those for competitive protocols.
1.0 ATELNET: An APPC Remote Terminal for OS/2
1.1 What is ATELNET?
ATELNET is an APPC remote terminal modeled after TCP/IP's TELNET program.
TELNET is generally provided free of charge when you purchase a TCP/IP imple-
mentation. Using ATELNET, you can control a window on a remote workstation.
Users on both workstations can type into the same window at the same time.
So, when I start a session to a remote workstation, a full-screen session
appears on that workstation. You can switch to it, watch what I type, and
type in your own things, if you like. Anything that appears on my screen
shows up on your screen, also. For example, I can type DIR and you can press
Enter.
For example, when Tim starts a session to Steve's workstation, Steve sees a
full-screen session appear on his workstation. He can switch to that
session, watch what Tim types, or type in commands himself. Any message or
command that appears on Tim's screen will also appear on Steve's screen.
1.2 Uses for ATELNET
To date ATELNET has been used to:
o Run existing applications remotely that were not designed as cooperative
processing applications
o Manage remote workstation configurations
o Teach remote users how to run certain OS/2 programs.
In general, most existing applications are not designed for cooperative proc-
essing. For example, it is not possible to run remotely the OS/2 PSTAT
command to find out which OS/2 processes are running on a remote workstation.
With ATELNET, you can log on to that workstation and run PSTAT. Similarly,
you can run full-screen text editors on a remote workstation. For instance,
using Extended Services or Networking Services/2, you can use ATELNET to
connect to someone else's workstation, change their node definitions (.NDF)
file and then change their running APPC configuration. If an APPC trans-
action program (TP) definition had to be added to all the workstations in a
network, I could easily do that as an administrator.
ATELNET is also useful as a teaching tool. Using ATELNET, you can show new
users how to perform some function even though they may be located at a
remote workstation. You can bring up a full-screen session for new users,
and they can watch you demonstrate the use of a function.
2.0 A User's Guide to ATELNET
ATELNET is invoked with only one parameter, the partner LU alias (or fully
qualified partner LU name) of an LU on the target workstation. After you
invoke ATELNET, the conversations will be established and you will be shown
an OS/2 command prompt that has been created on the target workstation.
2.1 Starting ATELNET
To start ATELNET, enter the following command:
ATELNET destination [flags]
A destination is either the partner LU alias or the fully qualified
LU name of an LU on the target workstation. The destination is
used as a fully qualified LU name if it contains a period. A partner LU
alias may be 1 to 8 characters. A fully qualified LU name consists of
a 1 to 8 character netid and a 1 to 8 character LU name separated by a
period (e.g., "NETID.LUNAME").
Flags:
-u userid (up to 10 characters)
-p password (up to 10 characters)
You will be prompted for a userid and password if they
are needed. If only a userid is specified, you will be
prompted for the password.
-m mode_name (up to 8 characters, default is "#INTER")
After you enter this command, ATELNET establishes the conversations.
2.2 Exiting ATELNET
To end ATELNET, type "EXIT" at the OS/2 command prompt at the controlling
workstation.
2.3 Common Problems
If ATELNET hangs while establishing its conversations, ATELNETD on the target
workstation may be unable to successfully ALLOCATE the second session. Check
the target workstation and make sure that the transaction program is defined
as FULL_SCREEN and that the ATNSPY.DLL file is in a subdirectory that is on
the LIBPATH.
If another error occurs, use the Extended Services or Networking Services/2
trace facility or CMTRACE to capture a trace of the APPC API. If you cannot
resolve/identify the problem, you may send the trace to me.
Some common problems include:
o Incorrect TP program type
SYMPTOM ATELNET establishes the sessions
then immediately closes them.
ATELNETD changes the Communi-
cations Manager icon.
EXPLANATION/RESPONSE The ATELNETD TP definition speci-
fies the program type as BACK-
GROUND. The program type must be
FULL_SCREEN.
3.0 Configuring ATELNET For Your Network
This section describes how to configure ATELNET, both with and without
Extended Services or Networking Services/2.
3.1 Configuring ATELNET Under Extended Services or Networking Services/2
Use this section as a guide to configure Extended Services or Networking
Services/2 through SNA Configuration Management panels. You can also use the
supplied ATELNET.NDF file as a template for editing your working node defi-
nitions file.
3.1.1 Configuring ATELNET On the Controlling Workstation
To more easily identify the target workstation, define a partner LU alias.
The partner LU alias is simply another name you can use to specify the
target, rather than using the fully qualified partner LU name every time you
want to connect to the target.
DEFINE_PARTNER_LU
FQ_PARTNER_LU_NAME(NETID.PARTNER) /* change this */
PARTNER_LU_ALIAS(TARGET)
MAX_MC_LL_SEND_SIZE(32767)
CONV_SECURITY_VERIFICATION(NO)
PARALLEL_SESSION_SUPPORT(YES);
If you are running Extended Services or Networking Services/2, ATELNET itself
defines the TP for the second conversation. However, if you are running OS/2
EE 1.2 or 1.3 without Extended Services or Networking Services/2, you must
define the TP for the second conversation.
You must also tell APPC how to find the target workstation. You must either:
o Configure a link directly to the target workstation
DEFINE_LOGICAL_LINK
LINK_NAME(TARGET)
ADJACENT_NODE_TYPE(LEARN)
FQ_ADJACENT_CP_NAME(NETID.PARTNER) /* change this */
PREFERRED_NN_SERVER(NO)
DLC_NAME(IBMTRNET)
ADAPTER_NUMBER(0)
DESTINATION_ADDRESS(X'400000000001') /* change this */
CP_CP_SESSION_SUPPORT(YES)
ACTIVATE_AT_STARTUP(NO);
Change the "NETID.PARTNER" name and the "DESTINATION_ADDRESS" field to
the control point name and LAN address of the target workstation.
o Configure a link to a network node and let the network node find the
target workstation.
Both the controlling and target workstations should have links to network
nodes in the same network (i.e., identical netids). If the workstations
connect to different network nodes, the network nodes must have a path on
which they can establish a connection. One recommendation is to define a
link from the controlling and target workstations to the same network
node.
DEFINE_LOGICAL_LINK
LINK_NAME(MYNN)
ADJACENT_NODE_TYPE(LEARN)
FQ_ADJACENT_CP_NAME(NETID.NN) /* change this */
PREFERRED_NN_SERVER(YES)
DLC_NAME(IBMTRNET)
ADAPTER_NUMBER(0)
DESTINATION_ADDRESS(X'400000000002') /* change this */
CP_CP_SESSION_SUPPORT(YES)
ACTIVATE_AT_STARTUP(NO);
Change the "NETID.NN" name and the "DESTINATION_ADDRESS" field to the
control point name and LAN address of your network node server.
3.1.2 Configuring ATELNETD On the Target Workstation
Configure a transaction program definition that the attach manager can use to
start the ATELNETD process. Following is a sample verb from a node defi-
nitions file:
DEFINE_TP
TP_NAME(ATELNETD)
FILESPEC(d:\work\atelnet\atelnetd.exe) /* change this */
CONVERSATION_TYPE(EITHER)
CONV_SECURITY_RQD(NO)
SYNC_LEVEL(CONFIRM)
TP_OPERATION(NONQUEUED_AM_STARTED)
PROGRAM_TYPE(FULL_SCREEN);
Change the FILESPEC field to specify the path where you installed the
ATELNETD.EXE program.
To avoid conflicts between the definitions for ATELNETD and other programs
which may be using the default TP support, configure the TP explicitly. Do
not use the default TP capability of Extended Services or Networking
Services/2.
If you do not specify IMPLICIT_INBOUND_PLU_SUPPORT(YES) on your
DEFINE_DEFAULTS verb you must specify a DEFINE_PARTNER_LU for each partner
that will be connecting to the target workstation. This will lead to addi-
tional configuration for every partner LU and is not recommended.
You do not need to define a local LU with Extended Services or Networking
Services/2, since you can use the control point LU which is already config-
ured (it is a required definition).
3.1.3 Enabling Security with ATELNET
To use security with ATELNET, change the CONV_SECURITY_RQD parameter on the
"ATELNETD" DEFINE_TP verb to CONV_SECURITY_RQD(yes). This parameter tells
Extended Services or Networking Services/2 that a userid and password are
required to start this transaction program. NS/2 compares the userid and
password with the ones that you supplied on the Extended Services or Net-
working Services/2 "Configuration Management" screens within the "Advanced
SNA" configuration options.
3.2 Configuring ATELNET without Networking Services/2 or Extended Services
Use the following steps as a guide to configure the Communications Manager.
You can use the ATELNET.CFG file supplied with the ATELNET executables and
tailor it to your needs.
Configuring ATELNET on OS/2 without
Extended Services or Networking Services/2.
Change all names in parenthesis to fit your environment.
These instructions assume that you are using token ring as your
DLC. Configure both the controlling and target workstations.
Before you start, you need to know:
the fully qualified network name
the token ring address of the workstation you will connect to
SNA Base
change
PU name - (CPNAME)
must be unique in the network
Network Name (NETID)
set auto-activate to YES
ENTER
DLC profiles
token ring
adapter 0 create/change
load dlc - YES
link stations - (number of machines you will connect to)
you may have to increase the number of link
stations defined in LAN Feature Profiles
free unused link - NO
congestion tolerance - 100
max RU size - 4096
the transmit buffer size in LAN Feature Profiles
must be 124 larger than this value (4120). Depending
upon your token ring card, you may have to lower
these values.
send window count - 4
recv window count - 4
C&SM LAN id - pick something
ENTER (everything else can default)
LU Profiles (do this only if you don't have a default LU defined)
create CPNAME
LU name - (CPNAME)
default LU - YES
NAU address - 00
LU session limit - 255
Max TPs - 0
ENTER
Skip down to:
Transmission Service mode profiles
create #INTER
comment - Interactive mode
min RU size - 256
max RU size - 16384
receive pacing limit - 8
session limit - 8
ENTER
Initial Session Limit profiles
create INIT400
min conwinners source - 4
min conwinners target - 0
num autoactive - 0
ENTER
go back up to:
Partner LU profiles
create (TARGET)
fully qualified PLU name - (NETID).(TARGET)
LU alias - (CPNAME)
PLU session limit - 8
Conv Security - Yes or No (easiest to configure is No)
DLC type - token ring
ENTER
type the destination address of the TARGET machine
ENTER
select ADD
mode name - #INTER
sess lim - INIT400
ENTER
select END
Remotely Attachable transaction program profiles
create ATELNETD
comment - ATELNET server
TP filespec - type in the full path of ATELNETD.EXE
sync level - Either
conv type - Either
Conv Security - Yes or No (easiest to configure is No)
TP operation - non queued AM started
TP name - ATELNETD
Important: type the TP name in ALL CAPS
program type - Full Screen
Remotely Attachable transaction program profiles
create ATELNET2
comment - ATELNET second conversation
TP filespec - type the full path of ATELNET.EXE
sync level - Either
conv type - Either
Conv Security - No
TP operation - queued operator started
TP name - ATELNET.RECEIVER
Important: type the TP name in ALL CAPS
ENTER (accept defaults)
NOTE: If you selected YES for conversation security, fill out a
conversation security profile.
4.0 Acknowledgments
I appreciate the help of my IBM associates in writing and testing this appli-
cation, and in writing and reviewing this paper (listed below alphabet-
ically):
o Marc Fiammante
o Steve Joyce
o Susan Schulken
o John Q. Walker
o Mike Wamboldt